System and Method for Establishing an Incident Communications Network

ABSTRACT

The present invention is directed to a system and method for providing an interoperable communications system including a plurality of otherwise disjunct communication systems each including at least one communications device. The system includes a plurality of system interface controllers each coupled to one of the communication systems and a common network for connecting the communication system and associated communications devices to the common network. A controller is coupled to each of the system interface controllers. The system interface controller being operable in response to commands from an authorized controller wherein the connection between each of the communication systems and the common network is controlled by a controller associated with, and authorized to control each communication system. The system provides an interoperable communications system between the otherwise disjunct systems wherein the communications devices for each system coupled to the common network are in communication therebetween.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.11/488,409, filed on Jul. 18, 2006, entitled “InteroperableCommunications System and Method of Use,” which is incorporated hereinby reference.

The '409 Application in turn claims priority to U.S. Provisional PatentApplication No. 60/595,578, filed on Jul. 18, 2005, entitled “SelectiveInteroperability In A Communications Network,” which is incorporatedherein by reference.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention generally relates to a communications system foruse by multiple agencies during an emergency or other incident, and moreparticularly, to an interoperable communications system for couplingseparate radio networks to a common network wherein the connection foreach radio network with the common network is separately controlled by acontroller associated with each radio network.

2. Background of the Invention

Private wireless communication networks, such as those used by publicsafety or commercial users, are typically isolated from one another andoften utilize different and incompatible technologies. Whileinteroperability products are available to interconnect such diversesystems, cooperation among the entities involved is often a barrier tofull implementation. Thus, prior art first responder communicationsystems exist wherein control of the resources of each organizationcoupled to the system is controlled by a central commander orcontroller. Each organization providing resources to the system mustrelinquish control of its resources to the central commander. Theorganization responsible for the operation of its radio system(s) may beunable or unwilling to grant control of its resources either to peerorganizations or to a higher-level organization.

Additionally, primitive “party-line” interconnect systems have beenimplemented, but users have control of only resources physically attheir location, and have no visibility to what resources other users mayhave interconnected.

Based on the foregoing, it is the general object of the presentinvention to provide an interoperable communications system thatimproves upon, or overcomes the problems and drawbacks associated withprior art communication systems.

BRIEF SUMMARY OF THE INVENTION

The present invention provides an interoperable communications systemincluding a plurality of separate communication systems each includingat least one communications device, a plurality of system interfacecontrollers each coupled to one of the communication systems and acommon network for connecting an associated communication system andassociated communications devices associated to the common network. Thesystem further includes a plurality of controllers each coupled to oneof the system interface controllers and the common network, each of thesystem interface controllers being operable in response to commands fromthe controller coupled thereto for connecting the communication systemand the associated communication devices to the common network fortransmitting and/or receiving messages transmitted over said commonnetwork. The connection between each of the communications systems andthe common network being controlled by said controller associated witheach of the communications systems. The plurality of communicationsystems being interconnected via the common network forming theinteroperable communications system wherein the communications devicesassociated with each of the communication systems are operable by usersof the other communication systems.

The present invention facilitates real-time interoperability amongcommunications systems while retaining within each organization controlof its own resources (e.g., radio channels or talkgroups). The presentinvention addresses communications during an “incident” which may be aminor event or a major disaster response. Resources may include, but arenot limited to: dispatchers, radio channels, radio talkgroups,individual radio users, telephone resources, and data resources such asdatabase access. A convenient means is provided for staff of eachorganization to connect and disconnect its resources to an “incident.”These functions will commonly be performed by dispatch personnel. Eachparticipant organization in an incident has a view of all resources thathave been assigned. Control of each resource is assigned to specificorganizations and/or individuals; only those organizations orindividuals can assign that resource to an incident.

Additionally, the present invention provides a method of interconnectinga plurality of discrete communication systems and associatedcommunications devices via a common network. The method includingenabling a plurality of users associated with each of a plurality ofcommunications system to control to the communications devicesassociated with each of the other communications systems.

The method includes establishing control privileges for connecting eachof the communications systems to the common network and permitting onlythose users with the control privileges to control interconnection ofeach of the communications system to the common network. Additionally,the method includes coupling each of the communications systems to thecommon network in response to commands from one of the users having thecontrol privileges for the communications system thereby interconnectingthereby communications devices associated with said coupledcommunications system to said common network.

In a preferred embodiment, the present invention provides a system forconnecting a plurality of discrete radio networks to a common network.The system includes a radio interface controller coupled to a radiointerface for each of the communications systems and a controllercoupled to the radio interface controller for control thereof. Each ofthe radio interface controller and the controller being coupled to thecommon network. The radio interface controller being operable inresponse to commands from the controller wherein control of theinterconnection of each radio network is controlled by a controllerassociated therewith.

The radio interface controller being connectable to various radionetworks of different types and utilizing different frequencies whereinthe present invention system provides for communication betweenotherwise non-compatible communications networks and devices.

Additional features and advantages of the invention will be set forth inthe description which follows, and in part will be apparent from thedescription, or may be learned by practice of the invention. Theadvantages of the invention will be realized and attained by thestructure particularly pointed out in the written description and claimshereof as well as the appended drawings.

It is to be understood that both the foregoing general description andthe following detailed description are exemplary and explanatory and areintended to provide further explanation of the invention as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS/FIGURES

The accompanying drawings, which are included to provide a furtherunderstanding of the invention and are incorporated in and constitute apart of this specification, illustrate embodiments of the invention andtogether with the description serve to explain the principles of theinvention. In the drawings:

FIG. 1 is a block diagram showing an overview of one embodiment of aninteroperable communications network in accordance the presentinvention.

FIG. 2 is a block diagram showing another embodiment of an interoperablecommunications network in accordance with the present invention.

FIG. 3 is a block diagram of one embodiment of an InteroperabilityWorkstation (IWS) controller in accordance with the present invention.

FIG. 4 is a block diagram of one embodiment of a Radio Network InterfaceController (RNIC) in accordance with the present invention.

FIG. 5 is an event flow diagram showing the creation of an incident inaccordance with the present invention interoperable communicationsnetwork.

FIG. 6 is a diagram showing one embodiment of a graphical user interface(GUI) for use with an IWS of the present invention.

FIG. 7 is a diagram showing one embodiment of a GUI in accordance withthe present invention for use with an IWS controller for contactingvarious other IWS controllers and networks within the system.

DETAILED DESCRIPTION OF THE INVENTION

As shown in FIG. 1, the present invention is directed to aninteroperable communications system, hereinafter referred to as “InteropSystem” generally referred to by the reference numeral 10, whichprovides for communication between a plurality of separate radionetworks 12. In the FIG. 1 embodiment, the Interop System 10 includesthe separate radio networks 12A, 12B and 12C each coupled to a commonnetwork 13 referred to as an Interoperability IP Network or hereinafteras the “Interop Network”. Each radio network 12A-12C includescorresponding communication devices 14A-14C respectively, which includemobile communication devices 14A-14C mounted in various vehicles.Although not shown, hand-held or other types of portable communicationsdevices 14 are also often utilized in the radio networks 12. Asdescribed following, users of the communication devices 14A-14C of eachradio network 12A-12C respectively can communicate to all other users ofeach of the radio networks 12A-12C via the Interop Network 13 inaccordance with the present invention.

Each of the radio networks 12A-12C also include typical antennas 16A-16Cand base consoles 18A-18C. The radio networks 12A-12C represent typicalradio networks utilizing one of various communications channelsincluding Very High Frequency (VHF), and Ultra High Frequency (UHF),among others, which are coupled together forming the Interop System 10in accordance with the present invention. For example, FIG. 1 includesdiagrams of various typical radio networks 12 including a two-channelsystem 12A, a single channel system 12B, and a trunked system 12C whichare each coupled to the Interop Network 13 and together form the InteropSystem 10 in accordance with the present invention.

Still referring to FIG. 1, the Interop System 10 includes at least oneradio network interface controller 20A-20C (herein referred to as“RNIC”) coupled to each of the radio networks 12A-12C respectively. EachRNIC 20A-20C is coupled to the corresponding radio network 12 as well asthe common Interop Network 13 and a controller 22 identified herein asan Interface Work Station (IWS). Each RNIC 20 is operable in response tocommands from one or more IWS controllers 22 designated as havingcontrol over the particular RNIC 20 for coupling an associated radionetwork 12 to the Interop Network 13 for the purpose of transmitting andreceiving messages to/from each of the other radio networks coupled tothe Interop Network. The two-channel radio network 12A includes twointerfaces RNIC 20A one for coupling each channel of the two-channelradio network to the Interop Network 13. Still referring to the radionetwork 12A, each of the two RNIC 20A interfaces are coupled to andcontrolled by a single IWS controller 22. However, in other embodimentsof the present invention, other configurations may be utilized includingwherein a single RNIC 20 is configured to connect both channels of atwo-channel network to the Interop Network 13 or wherein each RNIC 20Ais coupled to controllable by individual IWS controllers 22.

Still referring to FIG. 1, the Interop System 10 includes a router 24coupled between the Interop Network 13 and the RNICS 20 and IWScontrollers 22 for each radio network 12 for routing messagestransmitted therebetween via the Interop Network 13. Alternatively, inother embodiments of the Interop System 10, other types of data switchesor hubs may also be utilized instead of the data router 24.

In a preferred embodiment, the Interop System 10 transmits messagesbetween the multiple radio networks 12 via IP protocol over the InteropNetwork 13, however, the scope of the present invention is not limitedin this regard as any suitable transmission protocols and correspondingnetwork could be utilized.

Preferably, the present invention Interop System 10 is configured asoverlay architecture connectable to pre-existing radio networks 12A-12Cas shown in FIG. 2. Typically, an RNIC 20 and IWS controller 22 iscoupled to each existing radio network 12A-12C for connecting each radionetwork to the common Interop Network 13. In this embodiment, theexisting radio networks 12A-12C are usually left in place for normaloperation apart from the Interop System 10. Depending on the radionetwork 12 being coupled to the Interop Network 13, various types ofline interfaces 28 are utilized for coupling the RNIC 20 to theparticular radio network.

As shown in FIG. 2, the radio network 12A includes conventional basestations 30 or repeaters connected to base consoles 18A via conventionalconsole electronics 32A. A line interface 28A is provided for couplingthe RNIC 20A to the radio network 12A. Depending on the configuration ofthe radio network 12, the line interface 28 may include various knowninterfaces such as, local control interfaces (audio, push-to-talk (PTT),receiving indication), DC remote, tone remote, and ear and mouth (E & M)interfaces.

Alternatively, the RNIC 20C is connected to a trunked radio network 12Cvia an air interface 40C coupled to mobile radios 42C. In anotherembodiment, also illustrated in FIG. 2, the RNIC 20C can be coupled tothe radio network 12C via typical console electronics 32C and trunkingcontroller 44C.

Still referring to FIG. 2, the radio network 12B is coupled to theInterop Network 13 via the RNIC 20B coupled in-line in the existingradio network. Thus, the communications devices 14B are providedselective access to the Interop Network 13 via the RNIC 20B pursuant tocommands from the IWS controller 22B associated with the radio network12B or another authorized IWS controller 22.

Referring again to FIG. 2, a network administrator or manager 34including a network server 36 is coupled to the Interop Network 13 forcarrying out administrative duties related to the Interop Network.Alternatively, in other embodiments of the Interop System 10,configuration of the network can be implemented from endpoints such asthe IWS controllers 22 and RNIC 20 servers wherein a networkadministrative server is not required.

Referring now to FIGS. 1 and 3, each IWS controller 22 is coupled to theInterop Network 13 and the RNIC 20 for controlling the connectionbetween the associated radio network 12 and the Interop Network 13.Thus, the connection between each radio network 12 and the InteropNetwork 13 is controlled by the IWS controller 22 associated with eachradio network via the RNIC 20. This is a key feature of the presentinvention as control over each radio network 12 and the communicationdevices 14 associated therewith is maintained by an IWS controller 22coupled thereto. As set shown in FIG. 3, the IWS controller 22 includesa computer processor identified as incident controller 45 having a userinterface 48 including one or more of an audio interface 50 including aspeaker and microphone 52 and an I/O interface 54 including a keyboard,mouse, monitor, joystick, etc., collectively, identified by thereference numeral 56. A graphical user interface (GUI) 58 is providedcoupled to the I/O interface 54 for providing graphics based outputs toa user of the IWS controller 22 such as the GUI included in FIG. 6.

The IWS controller 22 includes an audio processor 60 coupled to theincident controller 45 and the audio interface 50 for processing audioinputs/outputs transmitted to and from the IWS controller respectively.The audio processor 60 converts data packets received by the IWScontroller 22 to audio signals and outputs the same to a user of the IWScontroller via the audio interface 50. Similarly, audio signals input tothe IWS controller are converted by the audio processor 60 and/or theincident controller 45 and transmitted to the appropriate recipient viaa network interface 62 and the Interop Network 13. In the preferredembodiment, audio signals are transmitted over the Interop Network 13using standard RTP or SRTP as appropriate for real time transmission ofaudio messages, however other protocols may be utilized.

The IWS controller 22 includes an endpoint registry 64 coupled to theincident controller 45 and the network interface 62 for storing addressinformation for all endpoints in the Interop System 10 including allRNIC 20 servers and all IWS controllers 22. Each endpoint in the InteropNetwork 13 periodically announces its presence to all other endpoints inthe Interop Network (the preferred embodiment uses IP multicast toperform this announcement). All other endpoints that receive thisannouncement add the originating endpoint to their endpoint registry 64.The endpoint registry 64 allows each endpoint to communicate directlywith any other endpoint in the Interop Network 13 without the need foran intervening server.

The IWS controller 22 also includes a configuration database 66 andconfiguration interface 68 coupled to the incident server and theInterop Network 13. The configuration database 66 is provided forstoring configuration data for the IWS controller 22 as well as otherIWS controllers 22 and RNIC 20 servers including public key informationfor each RNIC 20 and IWS controller 22 in the Interop System 10. Apreferred embodiment of the Interop System 10 utilizes a public keycryptography method for encrypting messages transferred over the InteropNetwork 13.

Each RNIC 20 is configured with a list of IWS controllers 22 that havepermission to control the operation of that RNIC which are stored in theconfiguration database 66 coupled to the RNIC. For security purposes,each RNIC 20 verifies that a received message is from one a trusted IWScontroller 22.

For message authentication, the preferred embodiment of the InteropSystem 10 uses public-key cryptography as follows: Each endpoint in thesystem (RNIC 20 or IWS controller 22) is assigned a private key and apublic key in accordance with standard key generation techniques. Theprivate key is stored only on the endpoint associated therewith. Thepublic key is distributed to all other endpoints in the network via theconfiguration interface 68. Messages from an endpoint to other endpointsare encrypted using the originating endpoint's private key. Messagesreceived by an endpoint are decoded using the originating endpoint'spublic key. If this decode process is successful, the message originatorand contents are securely authenticated.

The Interop System 10 provides for multiple authorized IWS controllers22 to control a particular RNIC 20 and thereby control connectionbetween the associated communications devices 14 and the Interop Network13. Typically, for use during incidences involving multiplemunicipalities or jurisdictions, or other events, resources includingradio networks 12 and the associated communication devices 14 may beshared by multiple organizations including wherein several or all of theorganizations may be permitted to exercise control over the sharedresources. The Interop System 10 provides for multiple organizations tocontrol shared radio networks 12 by designating each of the IWScontroller 22 for each of the multiple organizations as authorized tocontrol the RNIC 20 associated with the shared network. Thus, the RNIC20 is configured to include all authorized IWS controllers 22 asauthorized to provide instructions to the RNIC. Although the commandsare sent to the RNIC 20 as session invitations, the RNIC is configuredto accept all invitations from authorized IWS controllers 22.

Referring to FIG. 4, the RNIC 20 coupled to each radio network 12includes an incident controller 45, coupled to an audio processor 60, anendpoint registry 64, a configuration database 66 and a configurationinterface 68 as set forth above with respect to the IWS controller 22.The incident controller 45 is coupled to an associated radio network 12via a radio interface 28 and the Interop Network 13 via a networkinterface 62.

In operation, the IWS controller 22 creates an incident as set forth inthe event flow diagram 70 of FIG. 5 and described following. Anoperator, User A, via an IWS controller 22 (IWS A) initiates a newincident 72 (FIG. 5, step 73) using the create incident button 74 of theGUI 76. (GUI 76 is illustrated in FIG. 6). The incident controller 45assigns an IP address that will be used for voice communications for theincident 72 (the preferred embodiment uses an IP multicast address). IfUser A desires to talk to another IWS controller 22 (IWS B), he uses theGUI 76 via invitation button 77 associated with the incident 72 toselect a particular IWS controller 22 to invite to participate in theincident 72 (FIG. 5, step 75). A GUI 100 (FIG. 7) is utilized by an IWScontroller 22 for selection of another IWS controller to invite to anincident 72 or peer-to-peer talk group. In the FIG. 7 embodiment, eachagency having IWS controllers 22 available on the Interop System 10 isidentified on the GUI 100 (i.e., Lowell—102; Chelmsford—104;Billerica—106; Massachusetts State Police—108; FBI—110; University ofMassachusetts—112; Keyspan—114.) The user of an IWS controller canselect one or more IWS controllers 22 using the icons 116 identifyingeach IWS controller available. In this example, selecting the IWS Bcauses the incident controller 45 to look up and retrieve the address ofIWS B in the endpoint registry 64. The incident controller 45 then sendsan invitation to the particular IWS controller 22 selected using theInterop Network 13 (FIG. 5, step 77).

The incident controller on IWS B receives the invitation and provides anotification to the User B as to the invitation (FIG. 5, step 79). TheUser B may then accept or decline the invitation. Per the FIG. 5example, User B accepts the invitation at step 81. Upon User Bacceptance of the invitation, the incident controller 45 (of IWS B)sends an acceptance message to IWS A (FIG. 5, step 83) and the userthereof (User A) is alerted of the acceptance of User B at step 85.

Thereafter, the incident controllers 45 of both IWS A and IWS B directtheir respective audio processors 60 to start a bidirectional audiostream as follows: Audio input from the IWS microphone 52 is convertedto data packets (the preferred embodiment uses standard RTP or SRTP asappropriate) and is transmitted to the IP address assigned to theincident. This transmission may optionally be enabled by pressing a PTT(Push-To-Talk) button and disabled by the release of this button. Datapackets received on the assigned IP address are converted to audio andsent to the IWS speakers 52. Thus, User A and User B are now engaged ina full-duplex voice conversation via their respective IWS controllers 22(FIG. 5, event 88).

A preferred embodiment of the Interop System 10 uses the standard SIPprotocol with message encryption to transmit messages over the InteropNetwork 13. However, the routing of information/data over the InteropNetwork 13 can be via any suitable protocol thus, the scope of theInterop System is not limited with respect to a particular datatransmission protocol.

Still Referring to FIG. 5, following acceptance of an invitation toallocate its radio network 12 and associated communications devices 14,each IWS controller 22 must issue appropriate commands to the RNIC 20coupled to the designated radio network to connect the same to theInterop Network 13. Thus, each IWS user (FIG. 5, User A and User B)intends to allocate an RNIC 20 under their control (e.g. RNIC A and RNICB respectively) to participate in the incident. The operator of each IWScontroller 22 then uses a GUI such as the GUI 120, shown in FIG. 7, toselect an RNIC 20 (and associated radio network 12) allocated for theincident and for which the IWS controller 22 is authorized to control(FIG. 5, step 87). For example, the GUI 120 for Lowell (Lowell, Mass.)identifies an RNIC 20 for each of a Police F1—122; Police F2—124; PoliceTAC-5—126; Fire Primary—128; and Fire TAC-6—130. As indicated in theFIG. 7 example, the Lowell GUI 120 indicates only RNICs 20 for which theIWS controller 22 is authorized to control. Thus, the RNICs associatedwith other agencies do not appear on the GUI 120 of the IWS controllers22 associated with the Lowell agencies.

As set forth above, each incident 72 created includes a separate IPaddress designated for that incident. Thus, if multiple incidents occursimultaneously wherein the same organizations are invited to coupletheir resources to the Interop Network 13, the audio transmissions arecommunicated to the radio networks 12 via the separate IP addresses foreach incident 72. Accordingly the endpoint group for one incident 72 mayinclude some common resources such as the IWS controllers 22 as well asvarious different or common RNICs 20 and associated radio networks 12.

As further shown in FIG. 5, the incident controller 45 for each IWScontroller 22 then looks up and retrieves the IP address of the RNIC 20to be coupled to the Interop Network 13 in the endpoint registry 64. TheIWS controller 22 and/or incident controller 45 (FIG. 5, IWS A and IWSB) then sends an invitation to the retrieved address of the RNIC 20using the Interop Network 13. (FIG. 5, step 89). As set forth above, thepreferred embodiment uses the standard SIP protocol with messageencryption. The incident controller 45 on the designated RNIC 20receives the invitation and verifies (via the public keys stored in theconfiguration database 66) that the invitation is from an IWS controller22 that has permission to control that RNIC. If verified, the RNIC 20accepts the invitation, which causes the incident controller to send anacceptance message to the inviting IWS controller. (FIG. 5, step 91).The user of the IWS controller is notified of the acceptance by the RNIC20 at step 93.

To complete the coupling of the allocated radio network 12 to theInterop Network 13, the incident controller 45 on the RNIC 20 directsthe audio processor 60 to start a bidirectional audio stream as follows:Audio input from the connected resource (i.e., radio network 12) isconverted to data packets (the preferred embodiment uses standard RTP orSRTP as appropriate) and is transmitted to the IP address assigned tothe incident 72. This transmission may optionally be gated by either an“audio present” control signal from the resource, or by the audioprocessor 60 detecting that a sufficient audio signal is present. Datapackets received on the assigned IP address are converted to audio andsent to the connected resource i.e., radio network 12 and thereby theassociated communication devices 14). While such audio is being sent,the RNIC 20 will output an “audio present” control signal for use by theradio network 12. Still referring to the FIG. 5 example, all fourendpoints (IWS A, IWS B, RNIC A, RNIC B) are thereby engaged in afull-duplex voice conversation which is established by joining the samein an IP multicast group (FIG. 5, event 95). Thus, any audio sent by oneof the endpoints is received by all of the other endpoints.

Referring again to FIG. 6, the GUI 70 displays an activity log 82including displaying a chronological listing 84 of the communications ofeach communications device 14 coupled to the incident 72. Additionally,a message window 86 on GUI 70 displays text messages conveyed betweenIWS controllers 22 associated with an incident 72. The message window 86implements a text-messaging (or instant messaging) capability betweenthe IWS controllers 22 participating in an incident 72. Operators of theIWS controllers 22 enter a message in the bottom window 135 then clickthe send button 137; The message is then sent to all other IWScontrollers 22 which are currently members of the incident 72 andappears in the message window 86 of each of these IWS controllers. Asshown in FIG. 6, identification headings as to the source of themessages are appended to the displayed listing 84 and the transcriptions90 to identify the source of the transmission. This is one example ofhow the Interop System 10 provides more than just voice interoperabilitybetween discrete systems.

Still referring to FIG. 6, the GUI 70 also includes a member listing 92for each incident 72 that identifies each organization or radio network12 which have authorized coupling its associated radio network to theInterop Network 13 for the particular incident. Thus, the IWS controller22 has a visual display showing all organizations and associated radionetworks 12 coupled to the Interop Network 13 for each incident.

At any time during or following the completion of an incident 72, an IWScontroller 22 via a user thereof may terminate the coupling between anassociated radio network 12 for which the IWS controller is authorizedto control and the Interop Network 13.

Accordingly, each IWS controller 22 communicates with other IWScontrollers and RNIC 20 servers as peer-to-peer nodes in the InteropNetwork 13. Additionally, each RNIC 20 operates in response to commandsfrom an authorized IWS controller. Incident communications aretransmitted to all IWS controllers 22 and RNIC 20 servers coupled to anincident 72 using peer-to-peer multicast transmissions. Accordingly,each RNIC 20 and associated radio network 12 is coupled to the InteropNetwork 13 pursuant to commands from an authorized IWS controller 22.Thus, control of each radio network 12 is maintained by an IWScontroller 22 associated therewith.

Although, the above-identified embodiment of the invention illustrates asystem and method for coupling a plurality of radio networks 12 to theInterop Network 13, the present invention is not limited in this regardas other types of communications systems and networks can also becoupled to an Interop Network 13 in accordance with the presentinvention. For example, a public address system (e.g., the publicaddress system in a high school or college campus) can be coupled to theInterop Network 13 via an RNIC 20 server and appropriate interface suchthat agencies such as police or fire organizations can directly operateand communicate over the public address system via the Interop Network13. Thus, any type of discrete communications system can be coupled tothe Interop System in accordance with the present invention via an RNIC20 and appropriate interface.

Further, it is not required that the RNIC 20 and IWS controller 22reside on separate servers, thus the Interop system 10 disclosed can beintegrated directly into dispatch consoles present in an existingsystem. Alternatively, the interop system disclosed can be integrateddirectly into a computer-aided dispatch (CAD) system.

Additionally, the Interop system of the present invention can be used topermit discrete organizations, and the computer networks associatedtherewith, to be accessible to otherwise disjunct agencies or networks.For example, the present invention Interop System 10 can be utilized toprovide police unit field units access to data facilities residing on adatabase coupled to an otherwise disjunct network, such as a crimedatabase or floor plan of a building. Thus, the disclosed system can beused to selectively grant access to data sources, such as a database.

Another example of resources which are connectable to an Interop Systemof the present invention are video systems including video cameras, suchas surveillance or in-vehicle cameras wherein access to the video datacaptured thereby is selectively provided to other users of the Interopsystem.

As set forth above, many other types of communications devices can becoupled to an Interop System in accordance with the present inventionwherein selective access to certain resources is provided to otherorganizations and users thereof coupled to the system. Access is grantedand controlled only by authorized controllers associated with theresources.

Further, a pre-planned (“storm plan”) can be developed to facilitaterapid setup of an incident configuration in accordance with the presentinvention system. Also, the disclosed system can provide communicationsamong a defined subset of members (such as certain IWS controllers only,permitting dispatchers to “conference” off-the-air with respect to anincident group).

The foregoing description of embodiments of the invention has beenpresented for the purpose of illustration and description, it is notintended to be exhaustive or to limit the invention to the formdisclosed. Obvious modifications and variations are possible in light ofthe above disclosure. The embodiments described were chosen to bestillustrate the principals of the invention and practical applicationsthereof to enable one of ordinary skill in the art to utilize theinvention in various embodiments and with various modifications assuited to the particular use contemplated. It is intended that the scopeof the invention be defined by the claims appended hereto.

1. A method for establishing an incident communications network thatenables interoperable communications among communications resourcescontrolled by multiple organizations during an incident involvingemergency or pre-planned multi-organization communications, wherein anadministrator controls a set of communications resources within anorganization, comprising: upon an occurrence of an incident,establishing an incident identifier associated with the incident;establishing communications among communications resources controlled byadministrators that accept an invitation to be electronically coupled tothe incident communications network, wherein communications amongadministrators and communications resources are exchanged on one or morecommunications channels associated with the incident identifier; andgranting communication rights to communications resources, wherein therights granted for a communications resource are determined by anadministrator that controls the communications resource, wherein anadministrator retains control of communications resources that wereunder the control of the administrator prior to the start of theincident, wherein control is the ability to determine the capabilitiesof the communications resource that are made available to otherorganizations within the incident communications network.
 2. The methodof claim 1, wherein an administrator is a user or electronic controller.3. The method of claim 1, wherein the communications resources comprisecommunications devices, communications facilities, or data resources. 4.The method of claim 3, wherein communications devices include two-wayradio communications devices, push-to-talk devices, wireline telephones,wireless telephones, personal digital assistants (PDAs), smartphones,public address systems, group address systems, video cameras orsurveillance devices.
 5. The method of claim 3, wherein the incidentcommunications network includes audio and video communications devices.6. The method of claim 1, further comprising storing an identity of acommunications resource that accepts an invitation to participate in theincident communications network within a registry.
 7. The method ofclaim 1, further comprising transmitting a control message to aninterface controller associated with a communications resource thatcouples the communications resource to the incident communicationsnetwork.
 8. The method of claim 7, wherein the control message isencrypted.
 9. The method of claim 1, further comprising assigning aunique transport address to enable routing of communications or datawithin the incident communications network.
 10. The method of claim 1,further comprising establishing multiple incident communicationsnetworks, wherein communications resources are contained within morethan one incident communications networks simultaneously.